Rapid checkout after payment

ABSTRACT

A user&#39;s checkout information is stored for a certain amount of time, e.g., 10 minutes, after checkout, and the user is given the option of selecting a button to add one or more items for purchase and completing the purchase by adding the additional item(s) and approving the payment, without having to go through a complete checkout flow again.

BACKGROUND

Field of the Invention

The present invention generally relates to online shopping, and moreparticularly, to online shopping checkout and payments.

Related Art

Consumers traditionally shop at brick-and-mortar stores, where consumerstravel to the physical stores, shop for items, purchase the items, andtake possession of the items, all at the point of sale (POS). However,online shopping is become more and more popular for numerous reasons,including the convenience of shopping from the consumer's home or officeand the ability to shop multiple merchants around the world from theircomputing device, without ever having to leave their house or office.

Payments made through online shopping purchases are typically processedonline, either through the consumer submitting information about afunding source, such as a credit card, debit card, or bank account, orusing a payment provider, such as PayPal, Inc. of San Jose, Calif. Aftera consumer is finished shopping, e.g., placing selected items into anonline cart or basket, the consumer goes through a payment or checkoutflow. As part of the flow, the consumer enters the funding informationor payment provider login information, confirms the purchase details andtotal, and receives a confirmation that the payment was processed.

However, there are times when a consumer may want to add one or moreitems to the purchase after checkout is completed. In that situation,the consumer typically has to start the shopping and payment processover, e.g., by selecting the item(s) to purchase, adding them to thecart, selecting a shipping address, entering in payment information, andconfirming the payment. This can be tedious and inconvenient andpossibly leading to the consumer deciding not to make the additionalpurchase at that time.

Therefore, a need exits for a payment solution that overcomes thedisadvantages described above.

SUMMARY

According to one embodiment, a user's checkout information is stored fora certain amount of time, e.g., 10 minutes, after checkout, and the useris given the option of selecting a button to add one or more items forpurchase and completing the purchase by adding the additional item(s)and approving the payment, without having to go through a completecheckout flow again. In one embodiment, when the rapid checkout optionis no longer available, the button disappears. In another embodiment,after initial checkout, the user sees a timer that counts down theamount of time remaining for the user to select the rapid checkoutoption or button.

Once selected, the user may be directed to a shopping page, where theuser can shop and/or search for additional items for purchase. The usercan then select one or more items for purchase. An order page may bedisplayed to the user showing the previous items along with the newitems. The user can then review and confirm the purchase. As a result,the user does not need to go through the full checkout flow again (e.g.,login, entering shipping address, billing address, and/or paymentinformation). The additional items may be purchased from the samemerchant or from a different merchant/site.

These and other features and advantages of the present invention will bemore readily apparent from the detailed description of the embodimentsset forth below taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart showing a process a user performs to utilize arapid checkout function according to one embodiment;

FIGS. 2A and 2B are two exemplary flows illustrating at least a portionof a standard payment flow for a payment provider and a rapid checkoutflow for the payment provider, respectively, according to oneembodiment;

FIG. 3 is block diagram of a networked system suitable for implementingthe process described herein according to an embodiment; and

FIG. 4 is a block diagram of a computer system suitable for implementingone or more components in FIG. 3 according to one embodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

FIG. 1 is a flowchart showing a process 100 a user performs to utilize arapid checkout function or option according to one embodiment. At step102, the user goes through a conventional checkout process. For example,the user may access a merchant site, seller site, marketplace site, orother site or mobile app that enables a user to shop and make apurchase. Access may be through a PC, computing tablet, smart phone, orother computing device. The purchase may be items, physical goods,digital goods, donations, services, etc. The user selects desired itemsfor purchase. Note that items, as used herein, may include one or moreof the different purchases listed above. The selected items may beplaced in a cart, which the user can review and edit if needed. The usercontinues by entering information for the purchase, such as shippingaddress, billing address for a credit card, and funding sourceinformation. Such information may be pre-populated if it was savedwithin the site. In that case, the user would simply need to confirm theinformation or revise if needed. If the information is not saved, theuser may need to manually enter the requested information.

If the user is paying with a payment provider, such as PayPal Inc. ofSan Jose, the user selects an appropriate button or link on the merchantpage. The user is then presented with a login screen, either as a newpage or a pop-up screen on the same page, requesting login information,such as a user identifier (e.g., user name, email address) and apassword or PIN.

Once the requested information has been entered or provided, the usermay confirm the order at step 104. Before confirmation, the user may bepresented with details of the purchase, such as item description, itemprices, total price, shipping costs, tax, etc. If the details areacceptable and correct, the user may select a “Confirm,” “Pay,” or otherbutton or link to confirm the order.

The payment and/or account information is then processed, such as by acredit card company, a bank, the merchant, a service provider, or apayment provider. If the payment can be approved, a notification is sentto the user and/or the merchant that the payment is approved orcompleted. A transaction number or identifier may accompany thenotification.

At this point, the user may conclude the current purchases with themerchant and await delivery of the purchased items. Alternatively, theuser may want to add one or more items to the purchase. This can happenwhen the user wants to add an item the user forgot to add or did notthink about adding during the shopping. Thus, at step 108, the usermakes a determination whether to add one or more items to the purchasejust completed. If the answer is no, the process ends and the user'sfunding source is debited, and the purchase is processed, such as themerchant shipping or otherwise delivering the purchased items.

However, if the user wishes to add an item, a determination is made, atstep 110, whether the user is within a time limit to add an item and usea rapid checkout option offered by the merchant and/or the paymentprovider. The user may be given a certain amount of time to use therapid checkout option. The amount of time may be determined by themerchant, the payment provider, or the user in various embodiments. Forexample, the payment provider may set the time at 5 minutes. Longertimes increase the likelihood that another person may make an authorizedpurchase from the user device or through the user session with themerchant. Shorter times may not give the user sufficient time to decidethat another item should be added. The user may also set a timer period,based on how much risk the user may be willing to take. For example, theuser may set a longer time to give the user more time in the event theuser wishes to add an item to a just concluded purchase. The useralternatively select a shorter time to minimize exposure, especially ifthe user expects to make a decision to add an item in a very short timeafter a purchase is confirmed.

In one embodiment, the user may set different time periods for differentmerchants or dollar amounts. For example, the user may set a longerperiod for larger merchants and merchants the user typically makeslarger purchases from. Larger merchants have larger inventories, so itmay be more likely that the user will want to add an item with a largermerchant than with a smaller specialized merchant or seller. Shorterperiods may be set for merchants that the user typically makes single orsmall purchases from. The payment provider may also set different timeperiods for different users, such as based on the user's purchasehistory. For example, if the payment provider sees that the user, in thepast, has had to make several transactions with a particular merchant orgenerally within ten minutes after one transaction has concluded, thepayment provider may set the time period for the user at ten minutesgenerally or for one or more specific merchants. However, for anotheruser, the payment provider may set a time limit of five minutes becausethe user has many transactions within five minutes of anothertransaction with the same merchant, but no repeat transactions outsideof seven minutes. The merchant may also set time periods if desired orallowed by the payment provider. Note that this option may not beavailable to all users, depending on the user, the payment provider,and/or the merchant preferences.

If the rapid checkout option is available, the user may be shown abutton or link after receiving notification at step 106 that indicatesto the user that the rapid checkout option is available. In oneembodiment, a timer or clock shows the user time remaining to select therapid checkout option. Once the timer reaches zero or the option is nolonger available, the rapid checkout button may disappear. During thetime the rapid checkout option is available, the payment provider and/orthe merchant saves the information from the just concluded purchase,such as shipping address, billing address, funding source information,and/or cart or item information. When the rapid checkout option is nolonger available, the information is no longer saved.

If the user wishes to add an item after the first purchase and the rapidcheckout option is not available, the user may go continue shopping withthe merchant and add the item(s) at step 112. This may involve the userselecting a “Continue Shopping” button on the merchant site, which maythen present the user a home or shopping page. The user then selects thedesired item and performs a conventional checkout at step 102. Thus, theuser is required to go through the same or similar checkout process asbefore because the earlier used information is no longer saved oravailable for reuse. For example, the user may be asked to login to apayment provider again, enter shipping address, billing address, etc.

However, if the user decides to add an item while the rapid checkoutoption is available, the user may select the option at step 114, such asby tapping, clicking, or otherwise selecting a button or link on themerchant page, which may be on the same page as the notificationreceived at step 106. Once selected, a communication may be sent to themerchant and/or the payment provider to notify of the user's intent toadd one or more items and to use saved information from the earliertransaction to rapidly checkout. In one embodiment, this stops the clockor timer indefinitely. In other words, the user is not limited to whenthe user needs to complete the transaction to add the additionalitem(s). In another embodiment, the communication triggers another timerthat gives the user a certain amount of time to complete the add-onpurchase. Again, the time remaining to complete may be shown to theuser, such as in the form of a timer counting down.

The user may then add the additional item(s) at step 116. For example,the user may be redirected back to a shopping page of the merchant,where the user can select the desired item(s) to be placed in the user'sshopping cart. Once added to the cart, the user may then confirm theorder at step 104. Note that the user no longer needs to perform acheckout again at step 102, e.g., no need to enter shipping information,billing information, login information, and payment information. Theuser simply needs to confirm the payment and the new item(s) are quicklyand easily added to the previously submitted order.

In another embodiment, the newly added item(s) are processed as its ownorder, i.e., the newly added item(s) are not added to the previousorder. However, there are still advantages in that the user does notneed to go through a new checkout process to add the new item. The userpayment and shipping information are saved so that the user simply hasto confirm the new order.

As shown in FIG. 1, after the additional item(s) are added, the usergoes through the previously described steps, including step 108, wherethe user can add more item(s) again. Thus, the user may continue to additems as long as the rapid checkout option is available. For example,the timer may reset each time the user receives a notification at step106. In other embodiments, the user may be allowed only one or a finitenumber of uses of the rapid checkout option based on a first fullcheckout flow. Note that the one or more of the various steps describedabove may be performed in different order and/or combined as suitable.

FIGS. 2A and 2B are two exemplary flows illustrating at least a portionof a standard payment flow for a payment provider and a rapid checkoutflow for the payment provider, respectively. In FIG. 2A, the merchanthas implemented an “Express Checkout” option through the paymentprovider on the merchant site. Various steps in a payment flow areillustrated, starting with the user ready to pay or checkout afterdesired items have been placed in a merchant shopping cart and endingwith a confirmation that the user sees. When the user wants to add anadditional item to the purchase, the user may need to start over againby adding the item and checking out again with the newly added item in anew shopping cart.

However, if the merchant provides the rapid checkout option, such as abutton on the confirmation page, the user gets to the review pagedirectly. In the example flow in FIG. 2B, once the user selects therapid checkout option, the user is directed to the review page, showinginformation such as shipping information, billing information, etc. Ifthat is confirmed, the user may be redirected to the merchant site tocontinue shopping, where the user may then add the desired additionalitem(s) to the cart. In another embodiment, these two steps may beswapped, where the review page will then show the user the previouslypurchased items and the new item(s). The user does not have to login inagain with the payment provider.

For payment, the user may be redirected to the merchant website. As soonas the user selects the “Pay” button, a new payment provider call“DoUpdateExpressCheckoutPayment” is used to update the existing order.To be able to provide the ability to not require user login again to thepayment provider website and to match the new and the existing website,the payment provider token that is transferred within the API—merchantcommunication is used. The token may also be used to define the exacttime stamp for the rapid checkout option timer. The time stamp providedby payment provider gives exact information how long the rapid checkoutoption will be available to the user.

By saving user information for a certain period of time, the user mayobtain the benefit of using the rapid checkout option across differentmerchant sites with the same transaction. For example, the user canvisit different websites, add products to the cart and go through thecheckout flow without the need to login to the user's account again orenter shipping, billing, or funding information each time. All ordersmay be added to the same initial transaction if the rapid checkoutoption (such as calling DoUpdateExpressCheckoutPayment) is used everytime the user completes the payment process, assuming the rapid checkoutoption is still available at each merchant page. For example, the timeror time stamp may reset each time the user finishes adding item(s) toone merchant site.

In one example, after the user finishes payment at merchant A, the userselects the rapid checkout option and may then go to a site of merchantB. The user information is saved by the payment provider. The userplaces items in the cart at merchant B's site, reviews the cart, andapproves payment without having to login with the payment provider. Oncea notification is received, the user may again see the rapid checkoutoption. The user may select the option and then go to a site formerchant C. Again, the user information is saved. The user placesdesired item(s) in a cart through the merchant C site and proceeds withcheckout and payment without having to login with the payment provider.This can continue as long as the user wants to add additional items(either within a current merchant site or a different merchant site) andthe rapid checkout option is still available.

In the above example, the user may enter a URL address or select a linkfrom a search to enter a new merchant's site. The user may also select alink on the site of a merchant where the user just completed atransaction. The link may be to one or more products offered by adifferent merchant.

In one embodiment, the user sees a separate receipt or review page foreach separate merchant, although the payment is processed as onetransaction by the payment provider. In another embodiment, the usersees a single cumulative receipt or review page, listing items from eachseparate merchant on the same receipt. The payment provider processesthe payment through one user transaction and credits accounts separatelyto the appropriate merchants.

It is possible to use this functionality to show products of otherstores on any website to promote cross-selling between merchants orwebsites. In one embodiment, when the user has completed the checkout,the user may be shown additional items that may be of interest to theuser, such as suggested by the payment provider through the user'scurrent and/or previous purchases. The user can then add those items tothe user's just-completed transaction.

FIG. 3 is a block diagram of a networked system 300 configured to handlea transaction using a rapid checkout option, such as described above, inaccordance with an embodiment of the invention. System 300 includes auser device 310, a merchant server 340, and a payment provider server370 in communication over a network 360. Payment provider server 370 maybe maintained by a payment provider, such as PayPal, Inc. of San Jose,Calif. A user 305, such as a sender or consumer, utilizes user device310 to perform transactions using payment provider server 370, such asmaking multiple purchases from a single completed transaction using therapid checkout option described above.

User device 310, merchant server 340, and payment provider server 370may each include one or more processors, memories, and other appropriatecomponents for executing instructions such as program code and/or datastored on one or more computer readable mediums to implement the variousapplications, data, and steps described herein. For example, suchinstructions may be stored in one or more computer readable media suchas memories or data storage devices internal and/or external to variouscomponents of system 300, and/or accessible over network 360.

Network 360 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 360 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks.

User device 310 may be implemented using any appropriate hardware andsoftware configured for wired and/or wireless communication over network360. For example, in one embodiment, the user device may be implementedas a smart phone, personal computer (PC), personal digital assistant(PDA), laptop computer, and/or other types of computing devices capableof transmitting and/or receiving data, such as an iPad™ from Apple™. Theuser may use different user devices to perform different transactionsdescribed above.

User device 310 may include one or more browser applications 315 whichmay be used, for example, to provide a convenient interface to permituser 305 to browse information available over network 360. For example,in one embodiment, browser application 315 may be implemented as a webbrowser configured to view information available over the Internet. Userdevice 310 may also include one or more toolbar applications 320 whichmay be used, for example, to provide client-side processing forperforming desired tasks in response to operations selected by user 305.In one embodiment, toolbar application 320 may display a user interfacein connection with browser application 315 as further described herein.

User device 310 may further include other applications 325 as may bedesired in particular embodiments to provide desired features to userdevice 310. For example, other applications 325 may include securityapplications for implementing client-side security features,programmatic client applications for interfacing with appropriateapplication programming interfaces (APIs) over network 360, or othertypes of applications. Applications 325 may also include email, texting,voice and IM applications that allow user 305 to send and receiveemails, calls, and texts through network 360, as well as applications ormobile apps that enable the user to communicate, transfer information,and make payments through the payment provider using a rapid checkoutoption as discussed above. User device 310 includes one or more useridentifiers 330 which may be implemented, for example, as operatingsystem registry entries, cookies associated with browser application315, identifiers associated with hardware of user device 310, or otherappropriate identifiers, such as used for payment/user/deviceauthentication. In one embodiment, user identifier 330 may be used by apayment service provider to associate user 305 with a particular accountmaintained by the payment provider. A communications application 322,with associated interfaces, enables user device 310 to communicatewithin system 300.

Merchant server 340 may be maintained, for example, by a merchant orseller offering various products and/or services in exchange for paymentto be received over network 360. Merchant server 340 may be used for POSor online purchases and transactions. Generally, merchant server 340 maybe maintained by anyone or any entity that receives money, whichincludes charities as well as retailers and restaurants. Merchant server340 includes a database 345 identifying available products and/orservices (e.g., collectively referred to as items) which may be madeavailable for viewing and purchase by user 305. Accordingly, merchantserver 340 also includes a marketplace application 350 which may beconfigured to serve information over network 360 to browser 315 of userdevice 310. In one embodiment, user 305 may interact with marketplaceapplication 350 through browser applications over network 360 in orderto view various products, food items, or services identified in database345.

Merchant server 340 also includes a checkout application 355 which maybe configured to facilitate the purchase by user 305 of goods orservices identified by marketplace application 350. Checkout application355 may be configured to accept payment information from or on behalf ofuser 305 through payment service provider server 370 over network 360,such as at a physical POS or online. For example, checkout application355 may receive and process a payment confirmation from payment serviceprovider server 370, as well as transmit transaction information to thepayment provider and receive information from the payment provider(e.g., a transaction ID). Multiple merchant servers 340 may be networkedwith the payment provider server 370 so that user 305 may use the rapidcheckout option across multiple merchants and sites with a singletransaction started and completed with one merchant or site.

Payment provider server 370 may be maintained, for example, by an onlinepayment service provider which may provide payment between user 305 andthe operator of merchant server 340. In this regard, payment providerserver 370 includes one or more payment applications 375 which may beconfigured to interact with user device 310 and/or merchant server 340over network 360 to facilitate the purchase of goods or services,communicate/display information, and send payments by user 305 of userdevice 310 and as discussed above.

Payment provider server 370 also maintains a plurality of user accounts380, each of which may include account information 385 associated withindividual users. For example, account information 385 may includeprivate financial information of users of devices such as accountnumbers, passwords, device identifiers, user names, phone numbers,credit card information, bank information, or other financialinformation which may be used to facilitate online transactions by user305. Advantageously, payment application 375 may be configured tointeract with merchant server 340 on behalf of user 305 during atransaction with checkout application 355 to track and manage paymentrequests and purchases made by users using the rapid checkout option.

A transaction processing application 390, which may be part of paymentapplication 375 or separate, may be configured to receive informationfrom a user device and/or merchant server 340 for processing and storagein a payment database 395. Transaction processing application 390 mayinclude one or more applications to process information from user 305for processing a payment request and payment by the user selecting thefast checkout option as described herein. As such, transactionprocessing application 390 may store details of a payment request from auser or merchant. Payment application 375 may be further configured todetermine the existence of and to manage accounts for user 305, as wellas create new accounts if necessary, such as the set up, management, anduse of an account for the user.

FIG. 4 is a block diagram of a computer system 400 suitable forimplementing one or more embodiments of the present disclosure. Invarious implementations, the user device may comprise a personalcomputing device (e.g., smart phone, a computing tablet, a personalcomputer, laptop, PDA, Bluetooth device, key FOB, badge, etc.) capableof communicating with the network. The merchant and/or payment providermay utilize a network computing device (e.g., a network server) capableof communicating with the network. It should be appreciated that each ofthe devices utilized by users, merchants, and payment providers may beimplemented as computer system 400 in a manner as follows.

Computer system 400 includes a bus 402 or other communication mechanismfor communicating information data, signals, and information betweenvarious components of computer system 400. Components include aninput/output (I/O) component 404 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons orlinks, etc., and sends a corresponding signal to bus 402. I/O component404 may also include an output component, such as a display 411 and acursor control 413 (such as a keyboard, keypad, mouse, etc.). Anoptional audio input/output component 405 may also be included to allowa user to use voice for inputting information by converting audiosignals. Audio I/O component 405 may allow the user to hear audio. Atransceiver or network interface 406 transmits and receives signalsbetween computer system 400 and other devices, such as another userdevice, a merchant server, or a payment provider server via network 360.In one embodiment, the transmission is wireless, although othertransmission mediums and methods may also be suitable. A processor 412,which can be a micro-controller, digital signal processor (DSP), orother processing component, processes these various signals, such as fordisplay on computer system 400 or transmission to other devices via acommunication link 418. Processor 412 may also control transmission ofinformation, such as cookies or IP addresses, to other devices.

Components of computer system 400 also include a system memory component414 (e.g., RAM), a static storage component 416 (e.g., ROM), and/or adisk drive 417. Computer system 400 performs specific operations byprocessor 412 and other components by executing one or more sequences ofinstructions contained in system memory component 414. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor 412 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious implementations, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 414, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 402. In oneembodiment, the logic is encoded in non-transitory computer readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 400. In various other embodiments of thepresent disclosure, a plurality of computer systems 400 coupled bycommunication link 418 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A payment provider server comprising: anon-transitory memory storing information about an account of a userwith a payment provider; and one or more hardware processors coupled tothe non-transitory memory and configured to read instructions to causethe server to perform operations comprising: in response to the userinteracting with a merchant website displayed on a user device andselecting a checkout option, receiving a first payment request from themerchant website; in response to the receiving of the first paymentrequest, transmitting a token associated with the first payment requestto the merchant website; receiving login information to the account ofthe user with the payment provider and checkout information indicatingshipping and billing information to be used for the first paymentrequest; processing a first payment corresponding to the first paymentrequest from the account of the user with the payment provider to anaccount of a merchant associated with the merchant website; storing thecheckout information indicating the shipping and billing informationreceived for the first payment request with a specific time limit afterthe processing of the first payment corresponding to the first paymentrequest; in response to a subsequent interaction at the merchant websiteby the user device, presenting, based on the stored checkout informationand the subsequent interaction being within the specific time limit, arapid checkout option on the merchant website displayed on the userdevice, wherein the rapid checkout option would not be presented basedon the stored checkout information for interactions that are not withinthe specific time limit; providing on the merchant website displayed onthe user device a timer that indicates a length of time remaining forthe rapid checkout option to be available; monitoring for a secondpayment request comprising the token during the specific time limit; inresponse to the user interacting with the merchant website displayed onthe user device and selecting the rapid checkout option, receiving thesecond payment request comprising the token based on the monitoring; andprocessing a second payment corresponding to the second payment requestfrom the account of the user with the payment provider to the account ofthe merchant associated with the merchant website using the storedcheckout information without the need for the user to provide the logininformation to the account of the user with the payment provider.
 2. Theserver of claim 1, wherein the token is used for the processing of thesecond payment corresponding to the second payment request.
 3. Theserver of claim 1, wherein the processing of the second paymentcorresponding to the second payment request is performed withoutrequiring entry by the user of shipping address, billing address, orfunding source information.
 4. The server of claim 1, wherein the timerresets each time the user selects the rapid checkout option.
 5. A methodcomprising: in response to a user interacting with a merchant websitedisplayed on a user device and selecting a checkout option, receiving,by a processor of a payment provider server associated with a paymentprovider, a first payment request from the merchant website; in responseto the receiving of the first payment request, transmitting, by theprocessor, a token associated with the first payment request to themerchant website; receiving, electronically by the processor, logininformation to an account of the user with the payment provider andcheckout information indicating shipping and billing information to beused for the first payment request; processing, by the processor, afirst payment corresponding to the first payment request from theaccount of the user with the payment provider to an account of amerchant associated with the merchant website; storing, by theprocessor, the checkout information indicating the shipping and billinginformation received for the first payment request with a specific timelimit after the processing of the first payment corresponding to thefirst payment request; in response to a subsequent interaction at themerchant website by the user device, presenting, based on the storedcheckout information and the subsequent interaction being within thespecific time limit, a rapid checkout option on the merchant websitedisplayed on the user device, wherein the rapid checkout option wouldnot be presented based on the stored checkout information forinteractions that are not within the specific time limit; providing onthe merchant website displayed on the user device a timer that indicatesa length of time remaining for the rapid checkout option to beavailable; monitoring, by the processor, for a second payment requestcomprising the token during the specific time limit; in response to theuser interacting with the merchant website displayed on the user deviceand selecting the rapid checkout option, receiving, by the processor,the second payment request comprising the token based on the monitoring;and processing a second payment corresponding to the second paymentrequest from the account of the user with the payment provider to theaccount of the merchant associated with the merchant website using thestored checkout information without the need for the user to provide thelogin information to the account of the user with the payment provider.6. The method of claim 5, wherein the token is used for the processingof the second payment corresponding to the second payment request. 7.The method of claim 5, wherein the processing of the second paymentcorresponding to the second payment request requires no entry by theuser of shipping address, billing address, or funding sourceinformation.
 8. The method of claim 5, wherein the timer resets eachtime the user selects the rapid checkout option.
 9. A non-transitorymachine-readable medium having stored thereon machine-readableinstructions executable to cause a payment provider server associatedwith a payment provider to perform operations comprising: in response toa user interacting with merchant website displayed on a user device andselecting a checkout option, receiving a first payment request from themerchant website; in response to the receiving of the first paymentrequest, transmitting a token associated with the first payment requestto the merchant website; receiving login information to an account ofthe user with the payment provider and checkout information indicatingshipping and billing information to be used for the first paymentrequest; processing a first payment corresponding to the first paymentrequest from the account of the user with the payment provider to anaccount of a merchant associated with the merchant website; storing thecheckout information indicating the shipping and billing informationreceived for the first payment request with a specific time limit afterthe processing of the first payment corresponding to the first paymentrequest; in response to a subsequent interaction at the merchant websiteby the user device, presenting, based on the stored checkout informationand the subsequent interaction being within the specific time limit, arapid checkout option on the merchant website displayed on the userdevice, wherein the rapid checkout option would not be presented basedon the stored checkout information for interactions that are not withinthe specific time limit; providing on the merchant website displayed onthe user device a timer that indicates a length of time remaining forthe rapid checkout option to be available; monitoring for a secondpayment request comprising the token during the specific time limit; inresponse to the user interacting with the merchant website displayed onthe user device and selecting the rapid checkout option, receiving thesecond payment request comprising the token based on the monitoring; andprocessing a second payment corresponding to the second payment requestfrom the account of the user with the payment provider to the account ofthe merchant associated with the merchant website using the storedcheckout information without the need for the user to provide the logininformation to the account of the user with the payment provider. 10.The non-transitory machine-readable medium of claim 9, wherein the tokenis used for the processing of the second payment corresponding to thesecond payment request.
 11. The non-transitory machine-readable mediumof claim 9, wherein the processing of the second payment correspondingto the second payment request requires no entry by the user of shippingaddress, billing address, or funding source information.
 12. Thenon-transitory machine-readable medium of claim 9, wherein the timerresets each time the user selects the rapid checkout option.
 13. Theserver of claim 1, wherein the operations further comprise determiningthe specific time limit based on the merchant website, a dollar amountfor the second payment request, and/or a purchase history of the user.14. The method of claim 5, further comprising determining the specifictime limit based on the merchant website, a dollar amount for the secondpayment request, and/or a purchase history of the user.
 15. Thenon-transitory machine-readable medium of claim 9, wherein theoperations further comprise determining the specific time limit based onthe merchant website, a dollar amount for the second payment request,and/or a purchase history of the user.